Google Git
Sign in
android / platform / external / autotest / 75dd4afa47c9961ffa1d6318e13142d614526cee
commit75dd4afa47c9961ffa1d6318e13142d614526cee[log] [tgz]
authorandroid-build-team Robot <android-build-team-robot@google.com>Fri Jan 01 02:07:26 2021 +0000
committerandroid-build-team Robot <android-build-team-robot@google.com>Fri Jan 01 02:07:26 2021 +0000
tree970bfee28a0ee405c81505a96ecebf10ce798f23
parentbf5486c156ee88eec0c465e900add1cff9f83a54 [diff]
parentc8ab9dc9b0f6e617c56d4dbe9e44c27f228d37ee [diff]
Snap for 7058891 from c8ab9dc9b0f6e617c56d4dbe9e44c27f228d37ee to sc-release Change-Id: I544284f2da1eed13960be99a4e44a5c5cad62b2b
tree: 970bfee28a0ee405c81505a96ecebf10ce798f23
  1. bin/
  2. cli/
  3. client/
  4. contrib/
  5. database/
  6. docs/
  7. frontend/
  8. logs/
  9. metadata/
  10. results/
  11. server/
  12. site_utils/
  13. test_suites/
  14. tko/
  15. utils/
  16. venv/
  17. MODULE_LICENSE_LGPL ⇨ LGPL_LICENSE
  18. .gitignore
  19. .style.yapf
  20. __init__.py
  21. common.py
  22. CTS_OWNERS
  23. ENGPROD_OWNERS
  24. FINGERPRINT_OWNERS
  25. FIRMWARE_OWNERS
  26. global_config.ini
  27. INFRA_OWNERS
  28. LGPL_LICENSE
  29. LICENSE
  30. main.star
  31. METADATA
  32. moblab_config.ini
  33. OWNERS.android
  34. PRESUBMIT.cfg
  35. PRESUBMIT.py
  36. README.md
  37. ssp_deploy_config.json
README.md

Autotest: Automated integration testing for Android and Chrome OS Devices

Autotest is a framework for fully automated testing. It was originally designed to test the Linux kernel, and expanded by the Chrome OS team to validate complete system images of Chrome OS and Android.

Autotest is composed of a number of modules that will help you to do stand alone tests or setup a fully automated test grid, depending on what you are up to. A non extensive list of functionality is:

  • A body of code to run tests on the device under test. In this setup, test logic executes on the machine being tested, and results are written to files for later collection from a development machine or lab infrastructure.

  • A body of code to run tests against a remote device under test. In this setup, test logic executes on a development machine or piece of lab infrastructure, and the device under test is controlled remotely via SSH/adb/some combination of the above.

  • Developer tools to execute one or more tests. test_that for Chrome OS and test_droid for Android allow developers to run tests against a device connected to their development machine on their desk. These tools are written so that the same test logic that runs in the lab will run at their desk, reducing the number of configurations under which tests are run.

  • Lab infrastructure to automate the running of tests. This infrastructure is capable of managing and running tests against thousands of devices in various lab environments. This includes code for both synchronous and asynchronous scheduling of tests. Tests are run against this hardware daily to validate every build of Chrome OS.

  • Infrastructure to set up miniature replicas of a full lab. A full lab does entail a certain amount of administrative work which isn't appropriate for a work group interested in automated tests against a small set of devices. Since this scale is common during device bringup, a special setup, called Moblab, allows a natural progressing from desk -> mini lab -> full lab.

Run some autotests

See the guides to test_that and test_droid:

test_droid Basic Usage

test_that Basic Usage

Write some autotests

See the best practices guide, existing tests, and comments in the code.

Autotest Best Practices

Grabbing the latest source

git clone https://chromium.googlesource.com/chromiumos/third_party/autotest

Hacking and submitting patches

See the coding style guide for guidance on submitting patches.

Coding Style

Pre-upload hook dependencies

You need to run utils/build_externals.py to set up the dependencies for pre-upload hook tests.

Setting up Lucifer

Setting up Lucifer